Should we fix this in bundle.esm.js? We could look at the named exports and strip out any typedef {import(...)}s of the same name. In theory more maintainable than noticing when yarn test-devtools fails and trying to figure out why.

Looking inside bundle.esm.js, though, I don't entirely understand why that /** @typedef {import('./dom.js').DOM} DOM */ isn't stripped from the inlined components.js but it is stripped from the inlined report-renderer.js.

the contents of bundle.esm.js aren't of concern here, but bundle.esm.d.ts (which is only generated in the roll script, heh), but your suggestion is still applicable. I believe we might be able to just delete export type DOM = any; after tsc makes the file and everything will be hunky dory.

I mentioned bundle.esm.js because that's what bundle.esm.d.ts is generated from and I believe why bundle.esm.d.ts ends up with both a type and a class DOM.

But why bundle.esm.js has both a typedef and a class DOM in the first place (and not zero DOM typedefs or many DOM typedefs), I don't know, so this works for me :) 👍